Back to Blog

I Tried Grok And I Hate That I Like Parts Of It

I finally used Grok. It kills me to admit this. I kind of like it. I do not want to like it. I really do not want to like it. But here we are. My principles are intact. My aesthetic standards are compromised. This is uncomfortable.

Disliking a product on principle is easy. Disliking a product while enjoying its interface is a special kind of cognitive dissonance. I am living it.

What I Like

The UI is nice. That is the honest truth. The layout feels intentional. The typography is readable. The spacing is generous. The dark mode does not assault my eyes at three in the morning. Someone put thought into the visual design. Someone cared about the user experience. I appreciate that effort even when I resent its source.

1
Things I Like
3
Things I Hate
My Internal Conflict
???
My Regret

The interface responds quickly. The input field feels polished. The conversation history is easy to navigate. These are small victories. They are also the kind of details I try to replicate in my own projects. I am taking notes. I am also feeling guilty about taking notes.

What I Hate

It is owned by Elon. That fact colors every interaction. Every smooth animation feels like propaganda. Every helpful response feels like marketing. I cannot separate the product from the person. I do not want to separate them. The association is intentional. The branding is deliberate. I am not fooled.

The models suck. That is the technical assessment. They produce confident nonsense. They hallucinate with authority. They struggle with basic reasoning tasks that my one million parameter Glint handles without crying. The performance does not match the presentation. The polish hides the limitations. I notice the limitations.

A beautiful interface cannot fix a weak model. A strong brand cannot fix weak reasoning. I have learned this lesson repeatedly. I am watching it play out again.

The Buggy But Nice UI

The interface is buggy. Buttons sometimes do not respond. The chat history occasionally fails to load. The formatting breaks in unpredictable ways. These bugs exist alongside the nice design. The coexistence is frustrating. The frustration is familiar. I experience similar bugs in my own projects. The difference is that my bugs do not come with a billionaire attached.

The nice UI makes the bugs more noticeable. When something looks polished, users expect it to work. When it does not work, the disappointment is sharper. I understand this dynamic. I also benefit from it when users forgive my own buggy interfaces because they appreciate the effort. The cycle continues.

Why This Matters

I build tiny models. I care about efficiency. I care about open access. Grok represents the opposite philosophy. It is large. It is closed. It is tied to a specific brand and a specific person. My appreciation for its UI does not change my commitment to my values. It does complicate my emotional response. That complication is worth documenting.

Good design is universal. Good design can appear anywhere. Recognizing good design does not require endorsing its source. I can acknowledge a well-executed interface while rejecting the ideology behind it. This is a nuanced position. Nuance is difficult. Nuance is necessary.

Final Thoughts

I tried Grok. I liked the UI. I hated the ownership. I hated the model performance. I hated the bugs. I also liked the UI. The contradiction is real. The discomfort is real. The lesson is real.

I will keep building Glint. I will keep improving Chroma TTS. I will keep shipping open models. I will keep designing interfaces that feel good to use. I will keep separating the craft from the corporation. That separation is my compass. That separation is my peace.

If you try Grok, form your own opinion. If you like the UI, enjoy it. If you hate the ownership, reject it. Both responses are valid. Both responses can coexist. I am living proof.